Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1201

reference
477-tree-1
name
1201
tree-preservation-order

undefined

477-tpo-1
uprn
address-text
point
POINT (-1.023494 50.884003)
geometry
MULTIPOLYGON (((-1.023409 50.883994,-1.023413 50.884010,-1.023425 50.884025,-1.023443 50.884037,-1.023467 50.884045,-1.023493 50.884048,-1.023520 50.884046,-1.023544 50.884038,-1.023563 50.884027,-1.023575 50.884012,-1.023580 50.883995,-1.023576 50.883978,-1.023564 50.883963,-1.023545 50.883951,-1.023522 50.883943,-1.023495 50.883940,-1.023469 50.883943,-1.023445 50.883950,-1.023426 50.883962,-1.023414 50.883977,-1.023409 50.883994)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL